Night Owl 6

home *** CD-ROM | disk | FTP | other *** search

/ Night Owl 6 / Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso / 015a / vram386.zip / HRAM1.DOC < prev next >

Wrap

Text File | 1990-09-23 | 49KB | 1,845 lines

1 HRAM Version 1.0 User's Guide 2 Copyright This HRAM documentation and the software are copyrighted with all rights reserved. Under the copyright laws, neither the documentation nor the software may be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form, in whole or in part, without the prior written consent of Biologic, except in the manner described in this manual. The unregistered version of HRAM and accompanying documentation may be freely copied and distributed. Copyright (C) Biologic 1990. All rights reserved. First edition printed 1990. Printed in the United States. Software License Notice Your license agreement with Biologic, which is included with the product, specifies the permitted and prohibited uses of the product. Any unauthorized duplication or use of HRAM in whole or in part, in print, or in any other storage and retrieval system is forbidden. Licenses and Trademarks DESQview is a registered trademark of Quarterdeck Office Systems, Inc. MS-DOS and Windows are registered trademarks of Microsoft Corporation. VRAM/386 and HRAM are trademarks of Biologic. Biologic POB 1267 Manassas VA 22110 USA 3 Contents License Agreement and Disclaimer of Warranty 4 Introduction 5 Notes on Memory and Memory Addresses 7 Testing Your Memory with Chkmem 10 Condensed Instructions 11 Installation 13 hramdev.sys 15 hram.exe 17 hram.sys 20 Notes 22 Error Messages 23 Site License 27 Your Turn 28 4 License Agreement and Disclaimer of Warranty License agreement Disclaimer of warranty License agreement The terms of this license agreement apply to you and to any subsequent licensee of this HRAM software. Biologic retains the ownership of this copy of HRAM software. This copy is licensed to you for use under the following conditions. You may use the HRAM software on any compatible computer, provided the HRAM software is used on only one computer and by one user at a time. You may not provide use of the software in a computer service business, network, timesharing, multiple CPU or multiple user arrangement to users who are not individually licensed by Biologic, except that you may designate any employee to use such products on a one employee per license basis. You may not disassemble or decompile the HRAM software. Disclaimer of warranty Biologic excludes any and all implied warranties, including warranties of merchantability and fitness for a particular purpose. Biologic does not make any warranty of representation, either express or implied, with respect to this software program, its quality, performance, merchantability, or fitness for a particular purpose. Biologic shall not have any liability for special, incidental, or consequential damages arising out of or resulting from the use of this program. 5 Introduction Description Overview VRAM/386 and HRAM Highlights Requirements Contents of the HRAM disk Description HRAM is a powerful memory management program for 8088, 8086, 80286, 80386 and 80486 PCs that enhances the utilization of high memory (memory between 640K and 1024K). It uses the special mapping capabilities of EMS 4.0 expanded memory or Chips & Technologies shadow RAM to fill unused memory addresses in your PC's high memory, and create up to 944K of DOS memory. Depending on the hardware configuration of your PC, HRAM can create up to 96K of additional low DOS memory, and up to 208K of high DOS memory for use by TSRs and device drivers (such as network drivers). Overview HRAM is a set of programs that consists of: hramdev.sys, a device driver that fills unused high memory areas with expanded memory or shadow RAM. hram.exe, a program that loads TSRs into the high DOS memory created by hramdev.sys and can, optionally, increase the size of conventional memory. hram.exe also provides a status report of high memory and lists the programs that have been loaded into it. hram.sys, a special driver that loads device drivers into high memory. A utility program, Chkmem, is included in the package and provides information about the status of memory in your PC. VRAM/386 and HRAM The VRAM/386 and HRAM programs are designed to be completely compatible with one another. Although both will function alone--VRAM/386 creates EMS 4.0 expanded memory and HRAM converts expanded memory into high DOS memory--together they provide a complete memory enhancement package for 80386 PCs. 6 Highlights Compatible with all expanded memory boards that fully support the EMS 4.0 expanded memory specification. Compatible with all 80386 memory managers that fully support the EMS 4.0 expanded memory specification--including VRAM/386. HRAM, in conjunction with VRAM/386, supports the Microsoft VxD specification to ensure that HRAM is compatible with Windows 3.0. Compatible with Quarterdeck DESQview. Requirements A PC with a 8088, 8086, 80286, 80386 or 80486 microprocessor. IBM Personal Computer Disk Operating System (PC-DOS) or Microsoft Disk Operating System (MS-DOS) version 3.0 or greater. Minimum 256K of EMS version 4.0 expanded memory or Chips & Technologies shadow RAM. Contents of the HRAM disk The following files are included in the root directory of the distribution disk. hramdev.sys hram.exe hram.sys chkmem.exe read.me There may also be a \freeware directory which contains unregistered versions of our other software products. 7 Notes on Memory and Memory Addresses Conventional Memory Expanded Memory Extended Memory Memory Addresses Conventional Memory Conventional memory is located between 0K and 1024K and is the maximum amount of memory that can be addressed by the 8088 microprocessor on which the IBM PC is based.1 The designers of the original PC divided conventional memory space into a 640K block of memory to be used by MS-DOS programs (low DOS memory) and a 384K block of high memory for system hardware and ROM. The term, conventional memory, is sometimes used to refer just to memory from 0 to 640K. Expanded Memory Expanded memory is "paged" memory that can exist in 8088, 80286, and 80386 based PCs. As the memory requirements of programs grew, expanded memory was developed to support up to 32M of memory by swapping small blocks or "pages" of extra memory into the 1M address space of the 8088 processor so that only a few pages are addressable at a time. Memory pages that are not in use are stored as deactivated pages on an expanded memory board. The original expanded memory specification, EMS version 3.2, was developed jointly by Lotus, Intel, and Microsoft. Soon after, AST and Ashton-Tate developed a similar, but enhanced, specification called EEMS. These two specifications were replaced by EMS version 4.0, which incorporated features of both specifications. Below is a summary of a few important features: An expanded memory page is 16K in size. Expanded memory that conforms to the version 3.2 specification can be mapped only into a 64K region in high memory called the page frame. EMS version 4.0 supports the mapping of expanded memory into any location in conventional memory. A software control program, called an expanded memory manager, manages the placement of memory pages, and is typically loaded by the config.sys file when your PC is turned on or restarted. ____________________ 11K equals 1,024 bytes. 1024K equals 1,048,576 bytes or 1 megabyte. 8 Extended Memory Intel's newer processors, starting with the 80286, are capable of addressing memory above 1M--extended memory. Unfortunately, this memory is not addressable when these processors are in a processor state called real mode (a mode designed to maintain compatibility with the 8088) and cannot be fully utilized when using a real mode operating system such as MS-DOS. The problem of accessing extended memory while running MS-DOS has spawned several solutions: On PCs that support extended memory, a feature of the ROM BIOS allows programs to copy data between conventional and extended memory. Although programs cannot execute in extended memory, they can use it as storage space. Programs that take advantage of this feature include RAM disks, print spoolers, and 80286 expanded memory simulators. Protected mode run-time environments which allow an application program to execute in protected mode under MS- DOS. 80386 memory managers, like VRAM/386, that use the page mapping capability of the 80386 processor to convert extended memory into expanded memory and provide additional conventional memory for use by MS-DOS. Memory Addresses Memory addresses and ranges are typically specified using hexadecimal (hex) numbers. Hex numbers include the digits 0-9 and the letters A-F, giving 16 possible values for each hex digit. Conventional memory can be divided into 64 pages of 16K each. These pages can be referred to as page 0, page 1, page 2, and so on, or, as is the case in this manual, by their hexadecimal segment addresses. Using this notation, page 0 is at segment 0, page 1 is at segment 0400, page 2 is at segment 0800, etc. The following table lists some page numbers and their corresponding segment address and linear address: Segment Linear Page Address Address ________________________________ 0 0000 0K 1 0400 16K 2 0800 32K 3 0c00 48K 4 1000 64K 5 1400 80K 8 2000 128K 12 3000 196K 9 40 a000 640K 44 b000 704K 63 fc00 1,008K The first 40 pages (640K) of conventional memory are used by MS- DOS and the other 24 pages are reserved for system hardware and ROM. The exact usage of the upper 384K of conventional memory depends on the hardware configuration of your machine; typically, several blocks of this area are not used and are simply empty space. The table below lists the memory map of a typical PC: Address Range Description ________________________________________ 0000-a000 low DOS memory (640K) a000-c000 VGA display adapter (128K) c000-c800 hard disk controller (32K) c800-d000 unused address space (32K) d000-e000 expanded memory page frame (64K) e000-f000 unused address space (64K) f000- ROM 10 Testing Your Memory with Chkmem Put the distribution disk in drive A and enter the command [a:chkmem] to display the amount of expanded memory in your system and the amount of memory that is mappable above 640K. Example output is shown below: Biologic Chkmem, version 1.01 copyright (c) Biologic 1990. all rights reserved. 655360 bytes conventional memory 65536 bytes extended memory 0 bytes xms memory 3031040 bytes expanded memory 163840 bytes mappable memory above 640k If you have any "mappable memory above 640K", then HRAM can turn this memory into high DOS memory. If Chkmem displays 0 bytes of mappable memory above 640K, you cannot use HRAM because you do not have expanded memory in your PC (or it is not active) and you do not have shadow RAM. If you have expanded memory and you have only 65,536 bytes (64K) of mappable memory above 640K, your expanded memory is not fully compatible with the EMS version 4.0 specification since it can only be mapped to the 64K page frame in high memory. The lack of extra mappable memory limits HRAM's effectiveness. You can force HRAM to use the page frame (with the /f option), but this prevents other programs from utilizing expanded memory.2 The command [chkmem /e] will display additional information about the expanded memory in your PC, including a list of the segment addresses into which expanded memory can be mapped. ____________________ 2If you are using VRAM/386, you must use the VRAM/386 /h option to map high memory outside the page frame. See the VRAM/386 User's Guide for more information. 11 Condensed Instructions The following instructions briefly describe the installation and use of HRAM. If you are a knowledgeable computer user, you should be able to get HRAM working by following these steps. More detailed information can be found in the sections, "Installation", "hramdev.sys", "hram.exe", and "hram.sys". 1. Copy the files, hramdev.sys and hram.sys, to the root directory of drive C. Copy the files, hram.exe and chkmem.exe, to your directory for utility programs. 2. Add a line to your config.sys file that loads hramdev.sys as a device driver and restart your PC: device=hramdev.sys The location of this line in your config.sys file is important. It should be located immediately after the device driver that manages your expanded memory. If you are installing HRAM with VRAM/386, this line should be placed immediately after the line that loads the vram386.sys program. 3. Enter the command [hram /m] to list the memory region(s) into which TSRs and device drivers can be loaded. This command can also be used at any time to list the programs that have been loaded into high memory. The command [hram /a] will list the raw memory allocations in high memory. 4. If you are using a monochrome or a CGA display, you can use the hram program to convert up to 96K of your expanded memory into low DOS memory. Enter the command: hram/l 5. To load a TSR into a high memory region, use the command: hram [program] where [program] is the name of the TSR your want to load. You may specify a drive and/or path before the program name. If you do not specify a path, HRAM will search the Path string. 6. To load a device driver into a high memory region, insert the following line into your config.sys file: device=hram.sys [driver] where [driver] is the name of the device driver you want to load. You must include a path as part of the driver name. 12 13 Installation Preparing a boot disk Copying files hramdev.sys read.me Preparing a boot disk While installing HRAM, and determining your optimum configuration, there is a chance a program that has been loaded into high memory will not function properly and will "lock up" your PC during the boot process. For this reason, we recommend that you prepare a bootable floppy disk before installing HRAM, so that you can boot from drive A if necessary. To prepare a disk, format it with the /s option, so that it contains a copy of the MS-DOS operating system: [format a: /s]. Also, be sure to copy to the disk any required device drivers, such as a driver needed to control your hard disk, and create a config.sys file that loads the drivers. Verify that the disk boots properly before experimenting with HRAM. Copying files The files, hramdev.sys and hram.sys, should be copied to the root directory of drive C. The files, hram.exe and chkmem.exe, should be copied to the directory on your hard disk you use for utility programs. You should have a command in your autoexec.bat file which includes this directory in your Path so that your utility programs, including HRAM, can be executed from any directory on your hard drive.3 The following installation procedure assumes you have a directory called \util in the root directory of drive C. 1. Insert the distribution disk in drive A. 2. Type [copy a:*.sys c:\] (don't type the brackets). 3. Type [copy a:*.exe c:\util]. hramdev.sys Add a line to your config.sys file that loads hramdev.sys as a device driver and restart your PC: device=hramdev.sys The location of this line in your config.sys file is important. It should be located immediately after the device driver that manages your expanded memory. Drivers that manage expanded memory typically have "EMM" in their name. If you are installing HRAM with VRAM/386, this line should be placed immediately after the line that loads the vram386.sys program. ____________________ 3Read about the Path command in your DOS manual. 14 If the installation of hramdev.sys is successful, it reports: hram: high dos memory created during the boot process. Use the command [chkmem] to display the amount of high DOS memory in your PC. After hramdev.sys has been successfully installed, you can use hram.exe and hram.sys to install TSRs and device drivers into high DOS memory. hram.sys loads drivers into high memory with an appropriate [device=] line in your config.sys file. hram.exe loads TSRs into high memory, either from the DOS prompt or from a line in your autoexec.bat file. hram.exe also displays a status report of high memory usage. Read the sections "hram.sys" and "hram.exe" for more detailed information. If hramdev.sys reports an error, refer to the section "Error Messages". read.me Corrections to this user's guide and information about program enhancements are in the read.me file on the distribution disk. You can view this file by putting the disk in drive A and entering: [type a:read.me]. 15 hramdev.sys Command reference hramdev.sys creates high DOS memory into which device drivers and TSRs can be loaded. hramdev.sys works in conjunction with your expanded memory as follows: When your expanded memory manager is loaded, it searches for regions into which expanded memory pages can be mapped. Most managers automatically include conventional memory from 0 to 640K and all areas within high memory that are not in use by hardware devices or ROM. The 64K page frame is also allocated from the high memory area. hramdev.sys searches for mappable high memory, excluding the page frame, and maps expanded memory into those areas.4 It then builds control structures so DOS can use the additional memory. It is important to remember that the utility of HRAM is dependent on the capability of your expanded memory hardware. hramdev.sys can only create high DOS memory in areas your expanded memory can map. Some EMS version 4.0 boards do not fully implement the version 4.0 specification and cannot map expanded memory to segments outside the page frame. Command reference The format of the hramdev.sys command is device=d:\path\hramdev.sys [options] [options] specifies the optional hramdev.sys parameters described in the following section. The following options can appear in the hramdev.sys command. /e Use expanded memory only. hramdev.sys will not use Chips & Technologies shadow RAM to create high DOS memory. /f Use the expanded memory page frame for high DOS memory. The page frame is a 64K buffer in the high memory area into which expanded memory pages are mapped. Although EMS version 4.0 supports mapping of expanded memory to areas outside the page frame, most software programs, at a ____________________ 4the /f option causes hramdev.sys to include the page frame in high DOS memory. 16 minimum, require the page frame to be available. This option will create an additional 64K of high memory, but will, in most cases, prevent other programs from utilizing expanded memory. /i<addressrange> Include address range. The memory range specified by <addressrange> will be converted to high DOS memory. It must be above a000 (hex). <addressrange> is specified with hexadecimal segment addresses which must be multiples of 16K (0000, 0400, 0800, 0c00, 1000, 1400, ...). For example, to include the range c000 to c800 use the parameter [/ic000- c800]. Multiple include ranges should be separated by commas. For example, [/ic000-c800,e000-f000]. If /i is used, only the memory areas with the include range(s) will be available as high DOS memory. This option is useful only if there are mappable areas in high memory that should not be under the control of hramdev.sys. Normally, this option should not be used; hramdev.sys will automatically convert all mappable high memory (excluding the page frame) into high DOS memory. /n No pause on error. If hramdev.sys reports an error, it waits for you to press a key. This option causes hramdev.sys continue without waiting for a key. /s Use shadow RAM only. hramdev.sys will not use expanded memory to create high DOS memory. /x<addressrange> Exclude address range. This option prevents hramdev.sys from mapping a particular range of addresses. <addressrange> is specified with hexadecimal segment addresses which must be multiples of 16K. For example, to exclude the range c000 to c800 use the parameter [/xc000- c800]. Multiple exclude ranges should be separated by commas. For example, [/xc000-c800,e000-f000]. 17 hram.exe Displaying regions and programs in high memory Loading TSRs into high memory Increasing low DOS memory size Command reference Displaying regions and programs in high memory The command, [hram /m], will display a status report of the high memory created by hramdev.sys. As illustrated in the following example, the report lists the location and size of each high memory region as well as the TSRs and drivers that have been loaded: Biologic HRAM, version 1.0 copyright (c) Biologic 1990. all rights reserved. para- region address graphs bytes ------ ------- ------ -------- 0 c800 7ff 32752 1 e000 1000 65536 para- region address graphs bytes program ------ ------- ------ -------- ------- 0 c800 12e 4832 (block device) 0 c92e 1ea 7840 (char dev) mouse 0 cb18 30 768 (block device) 0 cb5a 4a5 19024 (avail) 0 12 288 other blocks 1 e000 24 576 scrnsave.com 1 e024 2d 720 fastkey.com 1 e051 5e 1504 unblink.com 1 e0af f51 62736 (avail) Note that each region is identified by a number, starting with 0, and that the report indicates into which region each TSR or device driver has been loaded. The amount of available space remaining in each region is listed also. The command, [hram /a], will list the raw memory allocations in high memory. 18 Loading TSRs into high memory hram.exe loads TSRs into the high DOS memory created by hramdev.sys. To load a TSR, specify the command you normally use to run the TSR as a parameter to the hram.exe program. To illustrate, suppose you wish to load a TSR program, called Notepad, into high DOS memory. The command you normally use to load it into low memory is: notepad /i The command to load it into high memory would be: hram notepad /i The HRAM command can be executed at the DOS prompt or it can be used within a batch file (including your autoexec.bat file). The file specified on the HRAM command line must be an "exe" or "com" file. Command reference The format of the HRAM command is hram [options] [program] [program options] [options] specifies the optional HRAM parameters described in the following section. [program] specifies the program to be loaded into high DOS memory. [program options] specifies the options for the program. The following options can appear in the HRAM command. /? Display help. /a List raw memory allocations in high DOS memory. Use this option to display the memory control blocks that have been allocated from high memory. /i Display registration information. This option causes hram.exe to list information about registering your copy of HRAM. If you have not purchased a registered copy of HRAM, and you continue to use it after a reasonable testing period, you are required to register your copy. /l Add pages to low DOS memory. If hramdev.sys has mapped a region in high memory starting at a000 (hex) and you have 19 exactly 640K of low DOS memory, you can use this option to add this region to the DOS memory pool--giving you up to 736K of low memory.5 This region is available only if you have a monochrome or CGA display, and your expanded memory is capable of mapping pages to the area starting at a000. You must execute [hram /l] before loading any programs into memory region 0. /m List regions and programs in high DOS memory. [hram /m] lists a status report of high memory, including the size and location of each memory region and program or device driver. Read the previous section, "Displaying regions and programs in high memory", for more information. /n No pause on error. If hram.exe reports an error, it waits for you to press a key. This option causes hramdev.sys continue without waiting for a key. /r<region> Load into memory region number <region>. This option causes HRAM to load the program into the specified memory region. For example, the following command would load the program, notepad.exe, into memory region 1: [hram /r1 notepad]. Without this option, HRAM loads the program into the first memory region in which the program fits. This option gives the user greater control over the placement of programs and may be useful in obtaining the optimum use of high memory. /u Remove pages from low DOS memory. This option removes the pages from low DOS memory that have been added by the command [hram /l]. hram.sys Command reference hram.sys loads device drivers into the high DOS memory created by hramdev.sys. To load a device driver, modify the line in your config.sys file so that it is a parameter to the hram.sys program. To illustrate, suppose you wish to load the device driver ansi.sys into high DOS memory. The line to load it into ____________________ 5To list high memory regions, use the command [hram /m]. If region 0 is at address a000, [hram /l] will add this region to low DOS memory. 20 low memory is:6 device=\dos\ansi.sys The command to load it into high memory is: device=hram.sys \dos\ansi.sys Command reference The format of the hram.sys command is device=hram.sys [options] [driver] [driver options] where [options] specifies the optional hram.sys parameters described in the following section. [driver] specifies the device driver to be loaded into high DOS memory. [driver options] specifies the options for the device driver. The following options can appear in the hram.sys command. /n No pause on error. If hram.sys reports an error, it waits for you to press a key. This option causes hram.sys continue without waiting for a key. /r<region> Load into memory region number <region>. This option causes hram.sys to load the device driver into the specified memory region. For example, the following command would load the device driver, ansi.sys, into memory region 1: [device=hram.sys /r1 ansi.sys]. Without this option, hram.sys loads the driver into the first memory region in which the driver fits. This option gives the user greater control over the placement of programs and may be useful in obtaining the optimum use of high memory. ____________________ 6This example assumes that "ansi.sys" is located in the directory \dos. 21 Notes The utility of HRAM depends entirely on the mapping capabiliy of your expanded memory--if your expanded memory cannot map pages to areas outside the page frame, HRAM's effectiveness will be severely limited. Consult your expanded memory user's manual or, if necessary, contact the manufacturer, for information on how to configure your expanded memory optimally. Some TSRs and device drivers do not function properly when loaded into high memory. If you encounter a problem after loading several device drivers and TSRs into high memory, determine which program is not working by loading and testing each program individually. HRAM will be able to use high memory more efficiently if your memory is divided into the fewest memory regions--a few large regions is better than a lot of small ones. You may be able to improve the configuration of your high memory by changing the location of certain hardware devices. For example, most expanded memory boards allow you to move the page frame to any free 64K memory area and most network adapters allow you to change the location of their ROM. 22 Error Messages hramdev.sys hram.exe hram.sys hramdev.sys emm error An error was returned by the expanded memory manager. emm is not ems 4.0 HRAM is not compatible with your expanded memory. HRAM requires expanded memory that is compatible with the EMS 4.0 memory specification. expanded memory manager not installed Your expanded memory is not active because your expanded memory manager is not installed. Expanded memory managers typically have "EMM" in their name and are loaded with a [device=] command in your config.sys. Make sure the line that loads hramdev.sys is after the line that loads your expanded memory manager. invalid parameter(s) One or more of the parameters on the hramdev.sys command line is not valid. mappable physical address array too large hramdev.sys is not compatible with your expanded memory manager. no mappable pages in include range Your expanded memory cannot be mapped to the memory range specified by the /i (include range) option. hramdev.sys can only use memory that can be mapped by your expanded memory. To list the memory segments that are mappable: remove the line in your config.sys file that installs hramdev.sys, restart your PC, use the command [chkmem /e]. no pages available in high memory area hramdev.sys is unable to create high DOS memory because your expanded memory can be mapped to the page frame only. This may occur because you have no unused areas in high memory, or, more likely, because your expanded memory does not fully support the EMS 4.0 specification. If you are using VRAM/386, you must use the VRAM/386 /h option to map high memory outside the page frame. See the VRAM/386 User's Guide for more information. no shadow ram 23 Your PC does not have Chips & Technologies shadow RAM or it is not compatible with HRAM. not enough expanded memory you do not have enough expanded memory to map all the mappable areas in high memory. hram.exe conventional memory size not 640K [hram.exe /l] will cause this error if conventional memory size (low DOS memory) is not exactly 640K (655,360 bytes). Use the Chkmem command to display the conventional memory size of your system. Some PCs, including IBM PS/2s, have a data area at the end of conventional memory, and do not have exactly 640K. environment too big hram.exe was not able to load the specified program because there was not enough room in high memory for the program's environment. hramdev.sys not installed The device driver, hramdev.sys, must be successfully loaded by your config.sys file in order for hram.exe to function properly. If, during the boot process, hramdev.sys does not display the message [hramdev: high dos memory created], then hramdev.sys was not loaded successfully. invalid parameter(s) One or more of the parameters on the hram.exe command line is not valid. missing parameters At least one parameter must be specified on the hram.exe command line: either the name of a program to load or an option. no memory available at a000h Memory region 0 does not begin at segment address a000 (hex). hram.exe can add pages to low DOS memory only if region 0 is at a000. [hram /m] will list the location and size of the regions in high memory. no memory has been added to low dos memory [hram /u] cannot remove pages from low memory because no pages have been added with [hram /l]. not enough memory to load program The memory requirements for loading and initializing the specified program exceed the size of the largest available memory block in high memory. Often, a program's memory 24 requirements during initialization are much greater than the program file size or size of the resident code. program has been loaded at a000h A program or device driver has already been loaded into region 0 and, therefore, region 0 cannot be added to low DOS memory. To prevent device drivers from being loaded into region 0 during the boot process, use the hramdev.sys /r option. program not executable The specified program is not an "exe" or "com" file. hram.exe can load executable files only. If you normally use a batch file to load the specified program, put the hram.exe command in the batch file. program not found The specified program was not found. Make sure the filename is correct and that it exists in the current directory or in a directory in your Path. hram.exe will not find the specified file if it is not an "exe" or "com" file. program not loaded The specified program was not loaded. region not found The region specified by the /r option does not exist. Use the command [hram /m] to display the location and size of all memory regions. there is no high dos memory hram.exe cannot load a program or display a memory report because there are no high DOS memory regions. hram.sys cannot get file size hram.sys was not able to load the specified device driver because it was unable to obtain the file size. device driver error while initializing hram.sys was not able to load the specified device driver because the driver returned an initialization error. This message is displayed whenever the device driver itself reports an error. Refer to the device driver's error message for help in correcting the problem. This error may occur if there is not enough high memory space. device driver not found The specified device driver was not found. Make sure the path and filename are correct. If you do not specify a path on the hram.sys command line, the device driver must be 25 located in the root directory of the boot drive. hramdev.sys not installed The device driver, hramdev.sys, must be successfully loaded by your config.sys file in order for harm.sys to function properly. The [device=] line that loads hram.sys must be located after the line that loads hramdev.sys. If, during the boot process, hramdev.sys does not display the message [hramdev: high dos memory created], then hramdev.sys was not loaded successfully. invalid parameter(s) One or more of the parameters on the hram.sys command line is not valid. memory region too small The memory requirements for loading and initializing the specified device driver exceed the size of the specified memory region. Often, a program's memory requirements during initialization are much greater than the program file size or size of the resident code. missing device driver name You must specify a device driver filename on the hram.sys command line. not enough memory to load device driver The memory requirements for loading and initializing the specified device driver exceed the size of the largest available memory block in high memory. Often, a program's memory requirements during initialization are much greater than the program file size or size of the resident code. region not found The region specified by the /r option does not exist. 26 Site License HRAM can be licensed on a per location basis which allows a company to use it on a network or use multiple copies of HRAM without purchasing them individually. Pricing is dependent on the number of copies and is very reasonable. Please contact Biologic for further information. 27 Your Turn We value you opinions. Please let us know what you like and dislike about the HRAM program and user's guide. We're dedicated to developing the most innovative and useful software available-- and selling it at reasonable prices. Your support helps make this possible. Please send all comments and suggestions to Biologic POB 1267 Manassas VA 22110 USA THANK YOU.